Because you didn't read the " !Read Me!" file. I even put exclamation marks in front of it and a space to put it at the top of your list. Read it first. Then, read this file. After you have read both, if the problem still persists, send me e-mail. (You will first, however, be required to answer one or more skill-testing questions to see if you actually did what I just told you to do.)
･Why doesn't the sound come out at the same time as I press a key?
This is QuickTime that is at fault. I have verified that the MIDI data is arriving in the program almost as soon as you press a key. However, when I call the QuickTime routine that is supposed to play the note, it doesn't always start right away. I have found that by turning off all or most of your extensions (Ram Doubler in particular seems to slow it down) it goes quicker, but still there is a noticeable time lag.
･Why does it take a long time to add the first track in a file?
Again this is QuickTime playing around with memory and what not. This is most likely caused because the first time you add a track, QuickTime decides that it needs to load all of the relevant QuickTime Music information into memory. QuickTime only loads code into memory that is being used by an application, in order to conserve memory for other uses. If I could make it go quicker, I would!
･Why does it take a long time to add a drum track?
QuickTime needs to load all of the drum sounds off of the disk. (I think. I am using the exact same calls as when loading any other instrument, so it's definitely not me wasting your time here...)
･How do I get it to work with Band In A Box?
It does. Upgrade to THIS version. Make sure you turn up the volume, since BIAB always seems to turn it off when it loads.
･Why is version 1.5 smaller than verions 1.4.1?
I turned off MacsBug names and streamlined some stuff... don't worry, you aren't missing out on anything!
･Please, Terry, tell me about QuickTime 2.5!
What? What about QuickTime 2.2? Well, there isn't going to be one. The next official version is 2.5 and it should be out "real soon". I have been beta testing version 2.5a7 and I can tell you that the Musical Instruments have seen a vast improvement! The delay between when a note is struck and when you hear it is virtually eliminated (at least on my 7500/100 it is. QuickTime 2.1 could even give my 7500/100 huge, long delays of up to 10 seconds! So clearly it has nothing to do with processor speed, but probably something to do with the time routines they're using.). That's very, very good news. And program changes appear to be quicker too. Also, many of the "Stuck Note" problems I have witnessed dissappear is version 2.5. Unfortunately, they seem to have added this "fade out" to the instruments. For example, an Acoustic String Ensemble instrument fades out after 4 or 5 seconds, instead of being sustained indefinitely. Very annoying. Also, the instruments sometimes turn themselves off and you have to open the "QuickTime Settings" control panel and toggle the buttons to get the instruments to turn back on. And after visiting the QuickTime Settings control panel, some of the API calls which never returned errors before (I always check to see if they do anyhow) return errors, just because you changed some stuff in the control panel. Very confusing. Finally, it appears that you may be able to finally use your own instruments. I have yet to see any documentation, but there are some new calls that seem to address the issue of creating your own instruments. We'll see... As soon as we developers get some good documentation on this stuff, things are poised to become very exciting! Hopefully by the time 2.5 is released all of these annoying little bugs will be cleaned out and we will have a great product in our hands!!!
(NOTE: QTMP will work fine with 2.5 when it's first released, so you won't need to upgrade or anything!)
